Method for constructing docking protocol by using direct communication, and apparatus therefor

ABSTRACT

Disclosed are a method for constructing a docking protocol for using a docking service in a direct communication system, and an apparatus therefor. To this end, a method by which a first wireless device constructs a docking protocol with a second wireless device comprises: a step for searching for a probe; a step for searching for a service; a step for enabling the first wireless device to construct an application service platform (ASP) session with the second wireless device; and a step for enabling the first wireless device to construct a docking protocol with the second wireless device. At this point, the step for constructing the ASP session can be selectively performed according to the capability or the device type of the first wireless device or the second wireless device.

TECHNICAL FIELD

The present invention relates to a wireless communication system, and more particularly, to a method and apparatus for establishing a docking protocol for use of a docking service in a direct communication system.

BACKGROUND ART

Recently, with the development of information communication technology, various wireless communication technologies have been developed. Of the technologies, wireless LAN (WLAN) is the technology that allows home or company or a specific service zone to access Internet wirelessly by using a portable terminal such as a personal digital assistant (PDA), a lap top computer, a portable multimedia player (PMP).

As direct communication technology that may allow devices to be easily connected with each other without a radio access point (AP) basically required in a conventional WLAN system, the introduction of Wi-Fi Direct or Wi-Fi peer-to-peer (P2P) has been discussed. According to Wi-Fi Direct, devices may be connected to each other even without a complicated establishment procedure. Also, Wi-Fi Direct may support a mutual operation for data transmission and reception at a communication speed of a general WLAN system to provide users with various services.

Recently, various Wi-Fi support devices have been used. Of the Wi-Fi support devices, the number of Wi-Fi Direct support devices that enable communication between Wi-Fi devices without AP has been increased. In Wi-Fi Alliance (WFA), technology for the introduction of a platform for supporting various services (for example, Send, Play, Display, Print, etc.) using Wi-Fi Direct link has been discussed. This may be referred to as Wi-Fi Direct Service (WFDS).

Besides the four predefined services, a new Wi-Fi Direct service capable of using peripheral functions provided by a different device is defined in the present invention.

DISCLOSURE OF THE INVENTION Technical Task

The technical task of the present invention is to provide a WFDS docking service, and more particularly, a method for establishing a docking protocol for a docking service.

Technical tasks obtainable from the present invention are non-limited the above-mentioned technical task. And, other unmentioned technical tasks can be clearly understood from the following description by those having ordinary skill in the technical field to which the present invention pertains.

Technical Solutions

In a first technical aspect of the present invention, provided herein is a method of establishing a docking protocol with a second wireless device by a first wireless device, including: transmitting, by the first wireless device, a probe request frame to the second wireless device; receiving, by the first wireless device, a probe response frame from the second wireless device in response to the probe request frame; transmitting, by the first wireless device, a service discovery request frame to the second wireless device; receiving, by the first wireless device, a service discovery response frame from the second wireless device in response to the service discovery request frame; establishing, by the first wireless device, an ASP (application service platform) session with the second wireless device; and establishing, by the first wireless device, the docking protocol with the second wireless device. In this case, the establishing the ASP session may be selectively performed according to a capability or a device type of the first wireless device or a capability or a device type of the second wireless device.

In a second technical aspect of the present invention, provided herein is a method of establishing a docking protocol with a second wireless device by a first wireless device, including: receiving, by the first wireless device, a probe request frame from the second wireless device; transmitting, by the first wireless device, a probe response frame to the second wireless device in response to the probe request frame; transmitting, by the first wireless device, a service discovery request frame from the second wireless device; transmitting, by the first wireless device, a service discovery response frame to the second wireless device in response to the service discovery request frame; establishing, by the first wireless device, an ASP (application service platform) session with the second wireless device; and establishing, by the first wireless device, the docking protocol with the second wireless device. In this case, the establishing the ASP session may be selectively performed according to a capability or a device type of the first wireless device and a capability or a device type of the second wireless device.

In a third technical aspect of the present invention, provided herein is a first wireless device, including a transceiver and a processor. In this case, the processor may control the transceiver to transmit a probe request frame to a second wireless device, receive a probe response frame from the second wireless device in response to the probe request frame, transmit a service discovery request frame to the second wireless device and receive a service discovery response frame from the second wireless device in response to the service discovery request frame, establish an ASP (application service platform) session with the second wireless device, and establish a docking protocol with the second wireless device. In this case, the processor may control the establishment of the ASP session to be selectively performed according to a capability or a device type of the first wireless device or a capability or a device type of the second wireless device.

In a fourth technical aspect of the present invention, provided herein is a first wireless device, including a transceiver and a processor. In this case, the processor may control the transceiver to receive a probe request frame from a second wireless device, transmit a probe response frame to the second wireless device in response to the probe request frame, receive a service discovery request frame to the second wireless device, and receive a service discovery response frame to the second wireless device in response to the service discovery request frame, establish an ASP (application service platform) session with the second wireless device, and establish a docking protocol with the second wireless device. In this case, the processor may control the establishment of the ASP session to be selectively performed according to a capability or a device type of the first wireless device or a capability or a device type of the second wireless device.

The above description and the following detailed description of the present invention are exemplary and are for additional explanation of the invention disclosed in the claims.

Advantageous Effects

According to the present invention, a WFDS docking service can be provided. Particularly, a method for establishing a docking protocol for a docking service between a wireless dockee and a wireless docking center can be provided.

Effects obtainable from the present invention may be non-limited by the above mentioned effect. And, other unmentioned effects can be clearly understood from the following description by those having ordinary skill in the technical field to which the present invention pertains.

DESCRIPTION OF DRAWINGS

The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the principle of the invention.

FIG. 1 illustrates a diagram for an example of a structure of IEEE 802.11 system to which the present invention is applicable.

FIG. 2 illustrates a diagram showing an exemplary Wi-Fi Direct network.

FIG. 3 illustrates a diagram showing a method for configuring a Wi-Fi Direct network.

FIG. 4 illustrates a diagram showing a neighboring discovery procedure.

FIG. 5 illustrates a diagram showing a new aspect of a Wi-Fi Direct network.

FIG. 6 illustrates a diagram showing a method for configuring a link for Wi-Fi Direct communication.

FIG. 7 illustrates a diagram showing a method for associating with a communication group that performs Wi-Fi Direct.

FIG. 8 illustrates a diagram showing a method for configuring a link for Wi-Fi Direct communication.

FIG. 9 illustrates a diagram showing a method for configuring a link that is associated with a Wi-Fi Direct communication group.

FIG. 10 is a diagram for explaining a WFDS framework configuration element.

FIG. 11 is a diagram for explaining a device discovery procedure and a service discovery procedure in WFDS.

FIG. 12 is a diagram illustrating a docking service in a simple way.

FIG. 13 is a diagram illustrating an example of using a docking service without ASP.

FIG. 14 is a diagram illustrating an example of using a docking service with ASP.

FIG. 15 is a diagram illustrating a procedure for establishing a docking protocol according to the present invention.

FIG. 16 is a block diagram for a configuration of a wireless device according one embodiment of the present invention.

BEST MODE FOR INVENTION

Reference will now be made in detail to the preferred embodiments of the present invention, examples of which are illustrated in the accompanying drawings. In the following detailed description of the invention includes details to help the full understanding of the present invention. Yet, it is apparent to those skilled in the art that the present invention can be implemented without these details.

Occasionally, to prevent the present invention from getting unclear, structures and/or devices known to the public are skipped or can be represented as block diagrams centering on the core functions of the structures and/or devices. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts.

Specific terminologies used for the following description may be provided to help the understanding of the present invention. And, the use of the specific terminology may be modified into other forms within the scope of the technical idea of the present invention.

Embodiments of the present invention may be supported by the disclosed standard documents of at least one of wireless access systems including IEEE 802 system, 3GPP system, 3GPP LTE system, LTE-A (LTE-Advanced) system and 3GPP2 system. In particular, the steps or parts, which are not explained to clearly reveal the technical idea of the present invention, in the embodiments of the present invention may be supported by the above documents. Moreover, all terminologies disclosed in this document may be supported by the above standard documents.

The following description may apply to various wireless access systems including CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), SC-FDMA (single carrier frequency division multiple access) and the like. CDMA can be implemented with such a radio technology as UTRA (universal terrestrial radio access), CDMA 2000 and the like. TDMA can be implemented with such a radio technology as GSM/GPRS/EDGE (Global System for Mobile communications)/General Packet Radio Service/Enhanced Data Rates for GSM Evolution). OFDMA can be implemented with such a radio technology as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, E-UTRA (Evolved UTRA), etc. UTRA is a part of UMTS (Universal Mobile Telecommunications System). 3GPP (3rd Generation Partnership Project) LTE (long term evolution) is a part of E-UMTS (Evolved UMTS) that uses E-UTRA. The 3GPP LTE adopts OFDMA in downlink (hereinafter abbreviated) DL and SC-FDMA in uplink (hereinafter abbreviated UL). And, LTE-A (LTE-Advanced) is an evolved version of 3GPP LTE.

For clarity, the following description mainly concerns IEEE 802.11 system, by which the technical features of the present invention may be non-limited.

Structure of WLAN System

FIG. 1 illustrates a diagram for an example of a structure of IEEE 802.11 system to which the present invention is applicable.

IEEE 802.11 structure may include a plurality of components and WLAN supportive of transparent STA mobility for an upper layer can be provided by interactions of the components. A basic service set (BSS) may correspond to a basic configuration block in IEEE 802.11 LAN. FIG. 1 shows one example that two basic service sets (BSS 1 and BSS 2) exist and that 2 STAs are included as members of each BSS. In particular, STA 1 and STA 2 are included in the BSS 1 and STA 3 and STA 4 are included in the BSS 2. In FIG. 1, an oval indicating the BSS can be understood as indicating a coverage area in which the STAs included in the corresponding BSS maintain communications. This area may be named a basic service area (BSA). Once the STA moves away from the BSA, it is unable to directly communicate with other STAs within the corresponding BSA.

A BSS of a most basic type in IEEE 802.11 LAN is an independent BSS (IBSS). For instance, IBSS can have a minimum configuration including 2 STAs only. Moreover, the BSS (e.g., BSS 1 or BSS 2) shown in FIG. 1, which has the simplest configuration and in which other components are omitted, may correspond to a representative example of the IBSS. Such a configuration is possible if STAs can directly communicate with each other. The above-configured LAN is not configured by being designed in advance but can be configured under the necessity of LAN. And, this may be called an ad-hoc network.

If an STA is turned on/off or enters/escapes from a BSS area, membership of the STA in a BSS can be dynamically changed. In order to obtain the membership in the BSS, The STA can join the BSS using a synchronization procedure. In order to access all services of the BSS based structure, the STA should be associated with the BSS. This association may be dynamically configured or may include a use of a DSS (distribution system service).

Layer Structure

The operation of the STA which is operated in the wireless LAN system may be described in view of layer structure. In aspect of device configuration, layer structure may be implemented by a processor. The STA may have a structure of a plurality of layers. For example, a layer structure handled by the 802.11 standard document mainly includes a MAC sublayer and a physical (PHY) layer on a data link layer (DLL). The PHY layer may include a physical layer convergence procedure (PLCP) entity, a physical medium dependent (PMD) entity, etc. The MAC sublayer and the PHY layer conceptionally include management entities called MAC sublayer management entity (MLME) and physical layer management entity (PLME), respectively. These entities provide a layer management service interface that operates a layer management function.

In order to provide exact MAC operation, an SME (Station Management Entity) is present within each STA. The SME is a layer independent entity that may be viewed as residing in a separate management plane or as residing “off to the side.” The exact functions of the SME are not specified in this document, but in general this entity may be viewed as being responsible for such functions as the gathering of layer-dependent status from the various layer management entities (LMEs), and similarly setting the value of layer-specific parameters. The SME may perform such functions on behalf of general system management entities and may implement standard management protocols.

The aforementioned entities interact in various ways. For example, the entities may interact by exchanging GET/SET primitives. The primitive means a set of elements or parameters related to a specific object. XX-GET.request primitive is used for requesting the value of the given MIB attribute (management information base attribute). XX-GET.confirm primitive is used for returning the appropriate MIB attribute value if status is “success,” otherwise returning an error indication in the Status field. XX-SET.request primitive is used for requesting that the indicated MIB attribute be set to the given value. If this MIB attribute implies a specific action, this requests that the action be performed. And, XX-SET.confirm primitive is used such that, if status is “success,” this confirms that the indicated MIB attribute has been set to the requested value, otherwise it returns an error condition in the status field. If this MIB attribute implies a specific action, this confirms that the action has been performed.

Also, the MLME and the SME may exchange various MLME_GET/SET primitives through MLME_SAP (Service Access Point). Also, various PLME_GET/SET primitives may be exchanged between PLME and SME through PLME_SAP, and may be exchanged between the MLME and PLME through MLME-PLME_SAP.

Evolution of Wireless LAN

Standards for Wireless Local Area Network (WLAN) technology have been developed by Institute of Electrical and Electronics Engineers (IEEE) 802.11 group. IEEE 802.11a and 802.11b use an unlicensed band at 2.4 GHz or 5 GHz. IEEE 802.11b provides a transmission rate of 11 Mbps and IEEE 802.11a provides a transmission rate of 54 Mbps. IEEE 802.11g applies Orthogonal Frequency-Division Multiplexing (OFDM) at 2.4 GHz to provide a transmission rate of 54 Mbps. IEEE 802.11n may use Multiple Input Multiple Output (MIMO)-OFDM, and provide a transmission rate of 300 Mbps. IEEE 802.11n may support a channel bandwidth up to 40 MHz to provide a transmission rate of 600 Mbps.

A direct link setup (DLS) related protocol under the environment according to IEEE 802.11e is based on QBSS (Quality BSS (basic service set)) that BSS supports QoS (Quality of Service). In QBSS, AP as well as non-AP STA is a QAP (Quality AP) that supports QoS. However, under the WLAN environment (for example, WLAN environment according to IEEE 802.11a/b/g) which is currently commercialized, although the non-AP STA is a QSTA (Quality STA) that supports QoS, the AP is likely to be a legacy AP that fails to support QoS. As a result, there is a limitation that DLS service cannot be used even in case of the QSTA under the WLAN environment which is currently commercialized.

Tunneled direct link setup (TDLS) is a wireless communication protocol which is newly suggested to solve such a limitation. TDLS, although not supporting QoS, enables QSTAs to set a direct link even under the WLAN environment such as IEEE 802.11a/b/g which is currently commercialized and set a direct link even in case of a power save mode (PSM). Accordingly, TDLS prescribes all the procedures for enabling QSTAs to set a direct link even at BSS managed by the legacy AP. Hereinafter, a wireless network that supports TDLS will be referred to as a TDLS wireless network.

Wi-Fi Direct Network

The WLAN according to the related art has mainly handled the operation of an infrastructure BSS that a radio access point (AP) functions as a hub. The AP performs a physical layer support function for wireless/wire connection, a routing function for devices on the network, and service provision for adding/removing a device to/from the network. In this case, devices within the network are not directly connected with each other but connected with each other through the AP.

As technology for supporting direct connection between devices, enactment of Wi-Fi Direct standard has been discussed.

FIG. 2 illustrates a diagram showing an exemplary Wi-Fi Direct network. The Wi-Fi Direct network is a network that enables Wi-Fi devices to perform device-to-device (D2D) (or peer-to-peer (P2P)) communication even without association with a home network, office network and hot spot network, and has been suggested by Wi-Fi Alliance. Hereinafter, Wi-Fi Direct based communication will be referred to as Wi-Fi Direct D2D communication (simply D2D communication) or Wi-Fi Direct P2P communication (simply, P2P communication). Also, a device that performs Wi-Fi Direct P2P will be referred to as Wi-Fi Direct P2P device, simply referred to as P2P device or Peer device.

Referring to FIG. 2, the Wi-Fi Direct network (200) may include at least one Wi-Fi device that includes a first P2P device (202) and a second P2P device (204). The P2P device may include Wi-Fi supporting devices, for example, a display device, a printer, a digital camera, a projector, a smart phone, etc. In addition, the P2P device may include a non-AP STA and an AP STA. In this example, the first P2P device (202) is a smart phone, and the second P2P device (204) is a display device. The P2P devices of the Wi-Fi Direct network may directly be interconnected. In more detail, P2P communication may mean that a signal transmission path between two P2P devices is directly configured in the corresponding P2P devices without passing through a third device (e.g., AP) or a legacy network (e.g., a network accessed to WLAN through an AP). In this case, a signal transmission path directly configured between two P2P devices may be limited to a data transmission path. For example, P2P communication may mean that a plurality of non-STAs transmit data (e.g., voice, image, text information, etc.) without passing through the AP. A signal transmission path for control information (e.g., resource allocation information for P2P configuration, wireless device identification information, etc.) may directly be configured between P2P devices (e.g., non-AP STA to non-AP STA, non-AP STA to AP), may be configured between two P2P devices (e.g., non-AP to non-AP STA) through the AP, or may be configured between the AP and the corresponding P2P device (e.g., AP to non-AP STA #1, AP to non-AP STA #2).

FIG. 3 illustrates a diagram showing a method for configuring a Wi-Fi Direct network.

Referring to FIG. 3, the Wi-Fi Direct network setup procedure may be largely classified into two procedures. The first procedure is a neighbor discovery (ND) procedure (S302 a), and the second procedure is a P2P link configuration and communication procedure (S304). Through the neighbor discovery procedure, the P2P device (e.g., 202 of FIG. 2) searches for another neighbor P2P device (e.g., 204 of FIG. 2) within (its own radio) coverage, and may obtain information required for association (e.g., pre-association) with the corresponding P2P device. In this case, the pre-association may mean a second layer pre-association in a radio protocol. For example, information required for the pre-association may include identification information of the neighbor P2P device. The neighbor discovery procedure may be carried out per available radio channel (S302 b). Afterwards, the P2P device (202) may perform Wi-Fi Direct P2P link configuration/communication with another P2P device (204). For example, after the P2P device (202) is associated with a peripheral P2P device (204), the P2P device (202) may determine whether the corresponding P2P device (204) is a P2P device incapable of satisfying service requirements of a user. To this end, after the P2P device (202) is second layer pre-associated with the peripheral P2P device (204), the P2P device (202) may search for the corresponding P2P device (204). If the corresponding P2P device (204) does not satisfy service requirements of the user, the P2P device (202) may sever the second layer association configured for the corresponding P2P device (204), and may configure the second layer association with another P2P device. By contrast, if the corresponding P2P device (204) satisfies the service requirements of the user, the two P2P devices (202 and 204) may transmit and receive signals through a P2P link.

FIG. 4 illustrates a diagram showing a neighboring discovery procedure. The example of FIG. 4 may be understood as an operation between the P2P device (202) and the P2P device (204) shown in FIG. 3.

Referring to FIG. 4, the neighbor discovery procedure of FIG. 3 may be initiated by indication of station management entity (SME)/application/user/vendor (S410), and may be classified into a scanning step (S412) and finding steps (S414 to S416). The scanning step (S412) may include the operation for scanning all available RF channels according to 802.11 schemes. Through the above-mentioned operation, the P2P device may confirm the best operation channel. The finding steps (S414 to S416) may include a listening mode (S414) and a search mode (S416). The P2P device may alternately repeat the listening mode (S414) and the search mode (S416). The P2P devices (202 and 204) may perform active search by using a probe request frame in the search mode (S416). For rapid search, the search range may be limited to social channels denoted by Channels #1, #6, #11 (2412, 2437, 2462 MHz). In addition, the P2P devices (202 and 204) may select only one channel from three social channels in the listening mode (S414), and maintain a reception status. In this case, if the other P2P device (e.g., 202) receives the probe request frame transmitted in the search mode, the P2P device (e.g., 204) generates a probe response frame in response to the received probe request frame. A time of the listening mode (S414) may be given at random (e.g., 100, 200, 300 time unit (TU)). The P2P devices continuously repeat the search mode and the reception mode so that they may reach a common channel. After the P2P device discovers another P2P device, the P2P device may discover/exchange a device type, a manufacturer, or a familiar device name by using the probe request frame and the probe response frame such that the P2P device may selectively be coupled to the corresponding P2P device. If the P2P device discovers the peripheral P2P device and obtains necessary information through the neighbor discovery procedure, the P2P device (e.g., 202) may notify SME/application/user/vendor of the P2P device discovery (S418).

Presently, P2P may be mainly used for semi-static communication such as remote printing, photo sharing, etc. However, due to generalization of Wi-Fi devices and location based services, P2P availability is gradually increased. For example, it is expected that the P2P device will actively be used for social chatting (for example, wireless devices subscribed to Social Network Service (SNS) recognize radio devices located in a neighboring region on the basis of the location based service and transmit and receive information), location-based advertisement provision, location-based news broadcasting, and game interaction between wireless devices. For convenience of description, such P2P application will hereinafter be referred to as new P2P application.

FIG. 5 illustrates a diagram showing a new aspect of a Wi-Fi Direct network.

The example of FIG. 5 may be understood as Wi-Fi Direct network aspect for use in the case in which new P2P application (e.g., social chatting, location-based service provision, game interaction, etc.) is applied.

Referring to FIG. 5, a plurality of P2P devices (502 a-502 d) performs P2P communication (510) in the Wi-Fi Direct network, P2P device(s) constituting the Wi-Fi Direct network may be changed at any time due to movement of the P2P device(s), and a new Wi-Fi Direct network may be dynamically generated or deleted within a short time. As described above, characteristics of the new P2P application indicate that P2P communication may dynamically be performed and terminated within a short time among a plurality of P2P devices in the dense network environment.

FIG. 6 illustrates a diagram showing a method for configuring a link for Wi-Fi Direct communication.

As shown in FIG. 6a , a first STA (610) (hereinafter, referred to as “A”) is being operated as a group owner during conventional Wi-Fi Direct communication. If the A (610) discovers a second STA (620) (hereinafter, referred to as “B”), which is a new Wi-Fi Direct communication target and does not perform Wi-Fi Direct communication, during communication with a group client (630) of conventional Wi-Fi Direct communication, the A (610) tries link setup with the B (620). In this case, new Wi-Fi Direct communication is Wi-Fi Direct communication between the A (610) and the B (620), and since the A is a group owner, the A may perform communication setup separately from communication of the conventional group client (630). Since one Wi-Fi Direct group may include one group owner and one or more group clients, as shown in FIG. 6b , a Wi-Fi Direct link may be set as the A (610) which is one group owner is satisfied. In this case, the A (610) invites the B (620) to the conventional Wi-Fi Direct communication group, and in view of Wi-Fi Direct communication characteristic, WFD communication between the A (610) and the B (620) and between the A (610) and the conventional group client (630) may be performed. Wi-Fi Direct communication is supported selectively based on the device's capability.

FIG. 7 illustrates a diagram showing a method for associating with a communication group that performs Wi-Fi Direct.

As shown in FIG. 7a , a first STA (710) (hereinafter, referred to as “A”) is performing communication as a group owner for a group client (730), and a second STA (720) (hereinafter, referred to as “B”) is performing communication as a group owner for a group client (740). As shown in FIG. 7b , the A (710) may terminate conventional Wi-Fi Direct communication and may perform association with a Wi-Fi Direct communication group to which the B (720) belongs. Since the A (710) is a group owner, the A (710) becomes a group client. Preferably, the A (710) terminates the conventional Wi-Fi Direct communication before requesting association with the B (720).

FIG. 8 illustrates a diagram showing a method for configuring a link for Wi-Fi Direct communication.

As shown in FIG. 8a , a second STA (820) (hereinafter, referred to as “B”) is being operated as a group owner during conventional Wi-Fi Direct communication. If the B (820) is performing conventional Wi-Fi Direct communication with a group client (830), a first STA (810) (hereinafter, referred to as “A”), which does not perform the Wi-Fi Direct communication, discovers the B (820) and tries link setup for new Wi-Fi Direct communication with the B (820). In this case, if the B (820) accepts link setup, a new Wi-Fi Direct communication link between the A (810) and the B (820) is set, and the A (810) is operated as a client of conventional Wi-Fi Direct group of the B (820). This case corresponds to the case where the A (810) performs association with the Wi-Fi Direct communication group of the B (820). The A (810) may only perform Wi-Fi Direct communication with the B (820) which is a group owner, and Wi-Fi Direct communication between the A (810). Wi-Fi Direct communication is supported selectively based on the device's capability.

FIG. 9 illustrates a diagram showing a method for configuring a link that is associated with a Wi-Fi Direct communication group.

As shown in FIG. 9a , a first STA (910) (hereinafter, referred to as “A”) is performing Wi-Fi Direct communication as a group client for a group owner (930). At this time, the A (910) discovers a second STA (920) (hereinafter, referred to as “B”), which is performing communication as a group owner for a group client (940) of another Wi-Fi Direct communication, and terminates a link with the group owner (930). And, the A (910) may perform association with Wi-Fi Direct of the B (920).

Wi-Fi Direct Service (WFDS)

Wi-Fi Direct is the network connection standard technology defined to include an operation of a link layer. Since the standard of an application operated in an upper layer of a link configured by Wi-Fi Direct is not defined, it is difficult to support compatibility in the case that the application is driven after devices which support Wi-Fi Direct are interconnected. To solve this problem, standardization of the operation of the upper layer application called Wi-Fi Direct Service (WFDS) has been discussed by the Wi-Fi Alliance (WFA).

FIG. 10 illustrates a diagram illustrating WFDS framework components.

A Wi-Fi Direct layer of FIG. 10 means a MAC layer defined by the Wi-Fi Direct standard. The Wi-Fi Direct layer may include software compatible with the Wi-Fi Direct standard. Wireless connection may be configured below the Wi-Fi Direct layer by a physical layer (not shown) compatible with WiFi PHY layer. A platform called an ASP (Application Service Platform) is defined above the Wi-Fi Direct layer.

The ASP is a logical entity that implements functions required for services. The ASP is a common shared platform, and may process tasks such as device discovery, service discovery, ASP session management, connection topology management and security between an application layer above the ASP and the Wi-Fi Direct layer below the ASP.

A service layer is defined above the ASP. The service layer includes use case specific services. The WFA defines four basis services, Send, Play, Display and Print services. The four basic services defined in the WFA will be described briefly. First of all, Send means service and application that may perform file transfer between two WFDS devices. The Send service may be referred to as a file transfer service (FTS) in that it is intended for file transfer between peer devices. Play means a service and application that shares or streams audio/video (A/V), photo, music, etc. based on DLNA (Digital Living Network Alliance) between two WFDS devices. Print means a service and application that enables documents and photos to be output between a device having contents such as documents, photos, and so on, and a printer. Display means a service and application that enables screen sharing between a Miracast source and a sink of WFA.

An enable API (Application Program Interface) shown in FIG. 10 is defined to use an ASP common platform in the case that a third party application in addition to basic service defined by the WFA is supported. The service defined for the third party application may be used by one application only, or may be used generally (or commonly) by various applications.

Hereinafter, for convenience of description, the service defined by the WFA will be referred to as a WFA service, and the service newly defined by the third party not the WFA will be referred to as an enable service.

The application layer may provide a user interface (UI), and serves to express information to be recognized by the user and transfer an input of the user to a lower layer.

Discovery Procedure in WFDS

FIG. 11 is a diagram for explaining a device discovery procedure and a service discovery procedure in WFDS. An ASP session setup operation shown in FIG. 11 means that a specific service of a random P2P device searches for another P2P device and service.

For convenience of description, in FIG. 11, it is assumed that device A is operated as a service advertiser for advertising its service and device B is operated as a service seeker for searching for a service.

If a service layer of the device A transmits Advertise Service Method to ASP, the ASP of the device A may advertise its service on the basis of information included in the Advertise Service Method and stand by to allow another device to discover the corresponding service.

If a service layer of the device B transmits Seek Service Method to ASP, the ASP of the device B may search for a device, which supports a higher application or a service desired by a user, on the basis of information included in the received Seek Service Method. For example, if the service layer of the device B receives information indicating intention to use a service (i.e., Use Service) from an application layer, the service layer may transfer the Seek Service Method, which includes information on the service that needs to be searched for, to the ASP.

Having received the Seek Service Method, the ASP of the device B may transmit a probe request frame to discover the device that supports the desired service. In this case, the probe request frame may include a hash value obtained by converting a service name of a service, which the device B desires to search for or may support, into a hash. The hash value is created by the ASP in a manner of converting the service name into a hash form and it may have a length of 6 octets. The probe request frame may be broadcasted or unicasted for a specific device.

Having received the probe request frame, the device A attempts hash matching. If determining that a service matched with the hash value included in the probe request frame is supported, the device A may transmit a probe response frame to the device B. In this case, the probe response frame may include at least one of a service name field and an advertisement ID field.

If receiving from the device A the probe response frame for indicating that the service, which the device B desires to search for, can be supported, the device B may transmit a service discovery request frame to discover service information of the device A. In this case, the service discovery request frame may include a service name field. The service name field include a complete service name desired to be searched for or a prefix of a service name desired to be searched for.

After performing service name matching, the device A may transmit to the device B a service discovery response frame for informing whether the service, which the device B desires to search for, is available. The service discovery response frame may include service name, service status, advertisement ID and service information. Here, the service name may include a string that indicates a service name of an advertised service.

However, the service discovery procedure is not mandatory so it may not be performed after the device discovery.

Based on the above description, the present invention proposes a new docking service besides the predefined WFDS. Hereinafter, the docking service defined in the present invention will be described in detail.

Wi-Fi Direct Docking

A Wi-Fi Direct docking service means a service that enables a first device to use peripheral functions provided by a second device after access to the second device. Here, the second device providing the peripheral functions to the first device may be referred to as a wireless docking center (WDC) (or Wi-Fi docking center) and the first device accessing to the WDC may be referred to as a wireless dockee (WD) (or Wi-Fi dockee).

The peripheral function is not part of the WD but it corresponds to a logical I/O (input/output) function, which can be used by the WD through access to the WDC. Moreover, a protocol that enables to use (or access) the peripheral functions through a Wi-Fi network may be referred to as a peripheral function protocol (PFP). For example, the PFP may include WSB (Wi-Fi serial bus) for utilizing I/O devices (e.g., camera, USB, etc.), which use a serial interface of the WDC, a Wi-Fi display or WiGig (wireless gigabits) display extension for using a display device of the WDC, etc. Furthermore, a group of one or more peripheral functions, which can be docked by the WD, may be referred to as a wireless docking environment (WDN).

FIG. 12 is a diagram illustrating a docking service in a simple way. When a docking service is initiated between a WD and a WDC, the WD may use peripheral functions provided by the WDC. For instance, if the WDC is a laptop, the WD may perform mirroring of the WDC or perform remote control of the WDC. Additionally, if the WDC is connected to another electronic device through USB, the WD may use the electronic device connected to the WDC. For example, if a printer is connected to the WDC through USB, the WD may be provided with an additional function such as printing by accessing the printer connected to the WDC.

Further, the WD may utilize a device paired with the WDC through Bluetooth (BT), a Bluetooth device connected through HDMI/DP/VGA, an audio device connected to the WDC, etc.

That is, the WD may mean a user device (e.g., smartphone, PDA, laptop) capable of using convenience functions provided by the WDC and the WDC may mean a device for connecting the peripheral functions to the WD and controlling the functions in order for the WD to have more user experience.

The WDC can be classified into a dedicated docking product to be used for a single purpose without association with peripheral devices and a multi-purpose peripheral connectivity hub for providing peripheral functions through association with peripheral devices. For example, the dedicated docking device may mean a device for a simple single-purpose without association with peripheral devices such as a printer dock for providing a print service, an audio dock for providing an audio output function, or a video dock (e.g., DVD player) for providing video and audio input/output. On the contrary, the multi-purpose peripheral connectivity hub may mean a device with expandability such as a laptop that can connected to a printer, an audio output device, a display device, etc.

To initiate the docking service, a docking protocol needs to be established between the WD and WDC. In this case, depending on whether the WD and WDC have capabilities of supporting ASP, the WD and WDC may create the docking protocol after establishing an ASP session or without ASP session establishment. Hereinafter, a procedure for creating a docking protocol between a wireless dockee and a wireless docking center will be described in detail.

Procedure for Docking Protocol Establishment

FIG. 13 is a diagram illustrating an example of using a docking service without ASP.

Referring to FIG. 13, first of all, a WD and WDC may perform a probe discovery procedure [S1301]. For instance, the WD may transmit a (P2P) probe request frame to discover the WDC. Having received the probe request frame from the WD, the WDC may transmit a probe response frame in response to the probe request frame.

The probe request frame and probe response frame may include at least one of P2P device identifier, P2P device information, service hash, and service name.

A service hash value may be determined from upper 6 bytes of a value obtained by converting a service name desired to be searched for into a hash through SHA256 algorithm. For example, a name of the docking service can be defined as “org.wi-fi.docking”. In this case, a string for identifying a type of the device desired to be searched for (e.g., wireless dockee or wireless docking center) may be additionally inserted into a lower layer of the service name.

For instance, a service name for discovering the WD may be defined as “org.wi-fi.docking.wd” by additionally inserting a string of “wd” and a service name for discovering the WDC may be defined as “org.wi-fi.docking.wdc” by additionally inserting a string of “wdc”.

A string for identifying whether the WDC supports a peripheral function or whether the WDC supports a peripheral function protocol may be additionally inserted into a lower layer of the identification characters for identifying the WDC.

For instance, “org.wi-fi.docking.wdc.pf” may be used as a service name for discovering the WDC that supports the peripheral function and “org.wi-fi.docking.wdc.pfp” may be used as a service name for discovering the WDC that supports the peripheral function protocol.

Further, a string for identifying a service provided using the peripheral function protocol may be further inserted into a lower layer of the identification characters for identifying the peripheral function protocol. For example, a name of a display service that uses the peripheral function protocol may be defined as “org.wi-fi.docking.wdc.pfp.display”, a name of a Wi-Fi serial bus service that uses the peripheral function protocol may be defined as “org.wi-fi.docking.wdc.pfp.wsb”, and a name of a WiGig display extension service that uses the peripheral function protocol may be defined as “org.wi-fi.docking.wdc.pfp.wde”.

A string for identifying the Wi-Fi serial bus service may be additionally inserted into a lower layer of the service name for identifying the docking service. For instance, a service name for discovering the Wi-Fi serial bus service may be defined as “org.wi-fi.docking.wsb.hub”.

The peripheral function protocol related to the Wi-Fi serial bus may be defined as i) camera and USB video class input in WSB, ii) USB audio class 2.0 input in WSB, iii) USB HID class in WSB, iv) WSB hub functionality, v) USB communication device class using a network control model in WSB, vi) Bluetooth USB HCI transport in WSB, vii) USB HID class in WSB, or viii) USB large-capacity storage device.

A string for searching for the dedicated docking device may be additionally inserted into the service name for identifying the docking service. For instance, a service name for discovering the dedicated docking device may be defined as “org.wi-fi.docking.wfd” by additionally inserting characters of “wfd”.

In this case, a string for searching for a service supported by the dedicated docking device may be additionally inserted into a lower layer of the string for identifying the dedicated docking device. For instance, “org.wi-fi.docking.wfd.sink.videoaudio” may be to discover a dedicated docking device for supporting video and audio input/output and “org.wi-fi.docking.wfd.sink.onlyvideo” may be to discover a dedicated docking device for supporting only video input/output.

When a wild card search (or prefix search) is used, it may include all services included in a prefix of a service name. For instance, if the service name includes a special character (e.g., ‘*’), all services included in a string before the special character, i.e., all services included in the prefix, may be searched for.

For instance, “org.wi-fi.docking.wdc.pfp*” may be used for discovering all services (e.g., “org.wi-fi.docking.wdc.pfp”, “org.wi-fi.docking.wdc.pfp.display”, “org.wi-fi.docking.wdc.pfp.wsb”, etc.) included in the prefix, “org.wi-fi.docking.wdc.pfp”. In this case, the WD may create a service hash value by converting “org.wi-fi.docking.wdc.pfp*” into a hash.

When the service hash value is included in the probe request frame, the WDC performs hash matching. If detecting a matched item on the basis of a hash matching result, the WDC may transmit the probe response frame including a service name to the WD.

If the device discovery is completed through the probe discovery procedure, a service discovery procedure may be initiated between the WD and WDC [S1302].

A service discovery request frame and a service discovery response frame may include service name, advertisement identifier, service information, etc. A service name field included in the service discovery request frame may contain a complete service name desired to be searched for or a prefix of a service name desired to be searched for.

Having received the service discovery request frame, the WDC performs service name matching. Thereafter, the WDC may transmit the service discovery response frame for informing whether the service, which the WD desires to search for, can be provided. The service discovery response frame may include a service name field for indicating a service name of an advertised service.

However, the WD and WDC may omit the service discovery procedure on the basis of their capabilities since the service discovery procedure is an optional procedure.

Thereafter, group owner negotiation may be initiated between the WD and WDC [S1304]. Particularly, the WD and WDC may determine a status of a group owner and a status of a client in a P2P group newly formed by the group owner negotiation.

As another example, one of the WD and WDC may participate in a P2P group of the other. Particularly, one of the WD and WDC may join an existing P2P group, which the other currently participates in, as a client.

In this case, when receiving a user input for indicating an attempt to dock with the WDC, the WD may send a docking request to the WDC [S1303].

As shown in the example, the WD may transmit a message for requesting docking with the WDC before establishment of an IP connection to the WDC.

As another example, after establishing the IP connection to the WDC and a docking protocol, the WD may transmit the message for requesting docking with the WDC by receiving a user input. In this case, establishment of a peripheral function protocol between the WD and WDC may be initiated by the docking request from the WD.

As another example, the WD may automatically send a docking request to the WDC at an appropriate time according to a default value.

If the group owner negotiation between the WD and WDC is completed or if one of the WD and WDC participates in the P2P group of the other, a P2P connection is established between the two devices and thus the two devices may be considered as being IP-connected to each other.

When the WD and WDC are IP-connected to each other, the two device may establish the docking protocol [S1305].

The docking protocol (or Wi-Fi docking protocol), which is newly proposed by the present invention, can support the following functions.

i) In a situation that the WD and WDC are docked with each other, the WDC may inform the WD of a peripheral function, a peripheral function protocol, or a wireless docking environment. In this case, the WDC may inform the WD of the above information by periods or through an event-driven method. As another example, the WDC may inform the WD of the above information according to a request from the WD.

ii) The WD and WDC may transmit or receive a message for requesting docking or undocking through the docking protocol.

iii) The docking protocol may form a security channel between the WD and the peripheral function, peripheral function protocol, or wireless docking environment.

iv) The docking protocol may provide a function of enabling the WD to reselect and use the peripheral function, peripheral function protocol, or wireless docking environment (e.g., WD-specific wireless docking environment or WDC-specific wireless docking environment).

v) The docking protocol may inform whether power save mode between the WD and WDC is supported or provide functions of checking and controlling the power save mode.

After the establishment of the docking protocol, the peripheral function protocol for using the peripheral function provided by the WDC may be established [S1306]. If the peripheral function protocol is established, the WD may use the peripheral function provided by the WDC through the peripheral function protocol [S1307].

If undocking between the WD and WDC is requested [S1308], a teardown of the peripheral function protocol and docking protocol between the WD and WDC may be performed [S1309]. In this case, the undocking may be requested by the WD or WDC.

After the teardown of the peripheral function protocol and docking protocol between the WD and WDC, the WD and WDC may terminate the P2P connection [S1310].

Next, a description will be given of an example of using a docking service with ASP.

FIG. 14 is a diagram illustrating an example of using a docking service with ASP.

Unlike FIG. 13, WD and WDC may establish a P2P connection through WFDS ASP after performing a probe discovery procedure [S1401] and a service discovery procedure [S1402].

Particularly, the WD may transmit a provision discovery request frame to the WDC and the WDC may transmit a provision discovery response frame in response to the transmitted provision discovery request frame. In this case, the provision discovery request frame and provision discovery response frame may include session information and connection capability for ASP session establishment.

The WD and WDC may initiate a group owner negotiation after establishing the ASP session through the provision discovery procedure. Particularly, the WD and WDC may determine a status of a group owner and a status of a client in a P2P group newly formed by the group owner negotiation.

As another example, if the ASP session is established between the WD and WDC, one of the WD and WDC may participate in a P2P group of the other. Particularly, one of the WD and WDC may join an existing P2P group, which the other currently participates in, as a client.

If the group owner negotiation between the WD and WDC is completed or if one of the WD and WDC participates in the P2P group of the other, the P2P connection is established between the two devices and thus the two devices may be considered as being IP-connected to each other.

When the WD and WDC are IP-connected to each other, the two device may establish an ASP coordination protocol [S1405]. The ASP coordination protocol may mean a protocol capable of controlling the ASP session.

After the establishment of the ASP coordination protocol, the two devices may establish a docking protocol [S1406] and a peripheral function protocol [S1407]. If the peripheral function protocol is established, the WD may use a peripheral function provided by the WDC through the peripheral function protocol [S1408].

If undocking between the WD and WDC is requested [S1409], a teardown of the peripheral function protocol and docking protocol between the WD and WDC may be performed [S1410]. In this case, the undocking may be requested by the WD or WDC.

After the teardown of the peripheral function protocol and docking protocol between the WD and WDC, the WD and WDC may terminate the P2P connection [S1411].

FIG. 14 illustrates that the WD sends a docking request to the WDC before the WD and WDC are IP-connected to each other [S1403].

As another example, the WD may request docking with the WDC during the provision discovery procedure by receiving a user input. In this case, the group owner negotiation between the WD and WDC may be initiated by the docking request from the WD. Alternatively, participation in the existing P2P group may be achieved by the docking request from the WD.

As another example, after establishing the IP connection to the WDC and the docking protocol, the WD may request docking with the WDC by receiving a user input. In this case, establishment of the peripheral function protocol between the WD and WDC may be initiated by the docking request from the WD.

Each of the procedures illustrated in the flowcharts of FIG. 13 and FIG. 14 is merely to show the order of steps and it does not mean that after completion of a step, the next step is initiated. In other words, each step of the procedures illustrated in the flowcharts of FIG. 13 and FIG. 14 may be initiated even though the previous step is not completed.

As shown in the examples of FIG. 13 and FIG. 14, the WD and WDC may use the docking service with the WFDS ASP (FIG. 14) or without the WFDS ASP (FIG. 13).

In this case, the WD and WDC may determine whether to use the ASP for use of the docking service according to a docking capability of each device or a type of the WDC.

FIG. 15 is a diagram illustrating a procedure for establishing a docking protocol according to the present invention. Since the method of using a docking service without ASP is described with reference to FIG. 13 and the method of using a docking service with ASP is described with reference to FIG. 14, an algorithm for determining whether to use ASP for use of a docking service is described with reference to FIG. 15.

Referring to FIG. 15, after performing a probe discovery procedure [S1501] and a service discovery procedure [S1502], WD and WDC may determine whether to use ASP for use of a docking service [S1504].

In this case, the WD and WDC may determine whether to use the ASP for the use of the docking service on the basis of an ASP supporting capability of each device.

For instance, if at least one of the WD and WDC does not support the ASP, the WD and WDC may establish a docking protocol without using the ASP. In this case, the WD and WDC may establish the docking protocol immediately after establishment of a P2P connection.

On the other hand, if both of the WD and WDC support the ASP, the WD and WDC may establish the docking protocol using the ASP. In this case, the WD and WDC may establish the docking protocol after establishment of an ASP session, P2P connection and ASP coordination protocol.

Information indicating whether the WD and WDC support the ASP may be exchanged through the service discovery procedure. However, since the service discovery procedure is optional, the information indicating whether the WD and WDC support the ASP may be exchanged through the probe discovery procedure instead of the service discovery procedure.

As another example, each of the WD and WDC may receive information indicating whether the other supports the ASP or not by performing the service discovery procedure mandatorily.

As another example, the WD and WDC may determine whether to use the ASP for the use of the docking protocol according to a type of the WDC.

For instance, when the WDC corresponds to a dedicated docking device, the WD and WDC may establish the docking protocol without using the ASP. In this case, the WD and WDC may establish the docking protocol immediately after the establishment of the P2P connection.

On the other hand, when the WDC corresponds to a multi-purpose peripheral connectivity hub, the WD and WDC may establish the docking protocol using the ASP. In this case, the WD and WDC may establish the docking protocol after the establishment of the ASP session, P2P connection and ASP coordination protocol.

In contrast to the above examples, when the WDC corresponds to the dedicated docking protocol, the docking protocol may be established using the ASP. When the WDC corresponds to the multi-purpose peripheral connectivity hub, the use of the ASP may be omitted.

In this case, the WDC may inform the WD of its type through the service discovery procedure. For example, the WDC may include a string indicating its own device type in a service name field of a service discovery response frame. In particular, when the WDC corresponds to the dedicated docking device, a string of ‘wfd’ may be included in the service name field. On the contrary, when the WDC corresponds to the multi-purpose peripheral connectivity hub, a string of ‘wdc’ may be included in the service name field.

As another example, the WDC may include information (e.g., 1 bit of information) indicating its device type in the service discovery response frame.

However, since the service discovery procedure is optional, the information on the device type of the WDC may be transmitted through the probe discovery procedure instead of the service discovery procedure. As a further example, the service discovery procedure may be performed mandatorily to enable the WDC to transmit the information on its device type to the WD.

FIG. 16 is a block diagram for a configuration of a wireless device according one embodiment of the present invention.

A wireless device 10 can include a display unit 11, a memory 12, a transceiver 13 and a processor 14. The transceiver 13 can transmit and receive a radio signal. For example, the transceiver can implement a physical layer according to IEEE 802 system.

The display unit 11 plays role in outputting information. A controller device can output a user interface for remotely controlling a controlling device through the display unit 11.

The processor 15 is electrically connected with the transceiver 13 and may be able to implement a physical layer and/or a MAC layer according to IEEE 802 system. And, the processor 11 can be configured to perform operations of encoding and decoding data for a control service.

A module for implementing an operation of a wireless device according to the aforementioned various embodiments of the present invention is stored in the memory 12 and can be executed by the processor 15. The memory 12 can be connected with the processor 11 by a means well-known to public in a manner of being included in the inside of the processor 15 or being installed at the outside of the processor 15.

A concreate configuration of the wireless device 10 shown in FIG. 16 can be implemented in a manner of independently applying the items mentioned earlier in the various embodiments of the present invention or applying two or more embodiments at the same time. For clarity, explanation on overlapped contents is omitted.

The embodiments of the present invention may be achieved by various means, for example, hardware, firmware, software, or a combination thereof.

In a hardware configuration, the methods according to exemplary embodiments of the present invention may be achieved by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, etc.

In a firmware or software configuration, an embodiment of the present invention may be implemented in the form of a module, a procedure, a function, etc. Software code may be stored in a memory unit and executed by a processor. The memory unit is located at the interior or exterior of the processor and may transmit and receive data to and from the processor via various known means.

Those skilled in the art will appreciate that the present invention may be carried out in other specific ways than those set forth herein without departing from the spirit and essential characteristics of the present invention. The above embodiments are therefore to be construed in all aspects as illustrative and not restrictive. The scope of the invention should be determined by the appended claims and their legal equivalents, not by the above description, and all changes coming within the meaning and equivalency range of the appended claims are intended to be embraced therein.

INDUSTRIAL APPLICABILITY

Although the aforementioned various embodiments of the present invention are explained centering on a Wi-Fi Direct system, the embodiments can also be applied to various mobile communication systems in a same way. 

1. A method of establishing a docking protocol with a second wireless device by a first wireless device, the method comprising: transmitting, by the first wireless device, a probe request frame to the second wireless device; receiving, by the first wireless device, a probe response frame from the second wireless device in response to the probe request frame; transmitting, by the first wireless device, a service discovery request frame to the second wireless device; receiving, by the first wireless device, a service discovery response frame from the second wireless device in response to the service discovery request frame; establishing, by the first wireless device, an ASP (application service platform) session with the second wireless device; and establishing, by the first wireless device, the docking protocol with the second wireless device, wherein the establishing the ASP session is selectively performed according to a capability or a device type of the first wireless device or a capability or a device type of the second wireless device.
 2. The method of claim 1, wherein if the second wireless device belongs to a first device type, the establishing the ASP session is omitted and wherein if the second wireless device belongs to a second device type, the docking protocol is established after the establishing the ASP session.
 3. The method of claim 2, wherein either the first or the second device type indicates that the second wireless device is a dedicated docking device and the other device type indicates that the second wireless device is a multi-purpose peripheral connectivity hub.
 4. The method of claim 2, wherein the service discovery response frame comprises identification information indicating the device type of the second wireless device.
 5. The method of claim 4, wherein the identification information is contained in a service name field of the service discovery response frame.
 6. The method of claim 5, wherein if the second wireless device is a dedicated docking device, the service name field comprises a string of ‘wfd’ and wherein if the second wireless device is a multi-purpose peripheral connectivity hub, the service name field comprises a string of ‘wdc’.
 7. The method of claim 5, wherein the service name field comprises a name of a docking service that the first wireless device desires to search for and wherein the identification information is contained in a lower level of the docking service name.
 8. The method of claim 1, wherein in case that the first wireless device transmits a message for requesting docking with the second wireless device to the second wireless device, the establishment of the docking protocol is initiated.
 9. The method of claim 1, further comprising establishing, by the first wireless device, a peripheral function protocol with the second wireless device after the establishment of the docking protocol.
 10. The method of claim 9, wherein if the first wireless device transmits a message for requesting undocking to the second wireless device, the docking protocol and the peripheral function protocol between the first and second wireless devices are torn down.
 11. The method of claim 1, the establishing the ASP session comprising: transmitting, by the first wireless device, a provision discovery request frame to the second wireless device; and receiving, by the first wireless device, a provision discovery response frame from the second wireless device in response to the provision discovery request frame.
 12. A method of establishing a docking protocol with a second wireless device by a first wireless device, the method comprising: receiving, by the first wireless device, a probe request frame from the second wireless device; transmitting, by the first wireless device, a probe response frame to the second wireless device in response to the probe request frame; transmitting, by the first wireless device, a service discovery request frame to the second wireless device; transmitting, by the first wireless device, a service discovery response frame to the second wireless device in response to the service discovery request frame; establishing, by the first wireless device, an ASP (application service platform) session with the second wireless device; and establishing, by the first wireless device, the docking protocol with the second wireless device, wherein the establishing the ASP session is selectively performed according to a capability or a device type of the first wireless device and a capability or a device type of the second wireless device.
 13. A first wireless device, comprising: a transceiver; and a processor, wherein the processor controls the transceiver to transmit a probe request frame to a second wireless device, receive a probe response frame from the second wireless device in response to the probe request frame, transmit a service discovery request frame to the second wireless device and receive a service discovery response frame from the second wireless device in response to the service discovery request frame, establishes an ASP (application service platform) session with the second wireless device, and establishes a docking protocol with the second wireless device and wherein the processor controls the establishment of the ASP session to be selectively performed according to a capability or a device type of the first wireless device or a capability or a device type of the second wireless device.
 14. A first wireless device, comprising: a transceiver; and a processor, wherein the processor controls the transceiver to receive a probe request frame from a second wireless device, transmit a probe response frame to the second wireless device in response to the probe request frame, receive a service discovery request frame from the second wireless device and receive a service discovery response frame from the second wireless device in response to the service discovery request frame, establishes an ASP (application service platform) session with the second wireless device, and establishes a docking protocol with the second wireless device and wherein the processor controls the establishment of the ASP session to be selectively performed according to a capability or a device type of the first wireless device or a capability or a device type of the second wireless device. 